Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1195

reference: 868-tree-1
name: 1195
tree-preservation-order: undefined
868-tpo-1
uprn
address-text
point: POINT (-1.044391 50.870245)
geometry: MULTIPOLYGON (((-1.044334 50.870239,-1.044337 50.870250,-1.044345 50.870260,-1.044357 50.870269,-1.044373 50.870274,-1.044391 50.870276,-1.044408 50.870274,-1.044424 50.870269,-1.044437 50.870261,-1.044445 50.870251,-1.044448 50.870240,-1.044446 50.870229,-1.044438 50.870219,-1.044425 50.870211,-1.044410 50.870206,-1.044392 50.870204,-1.044374 50.870205,-1.044358 50.870210,-1.044346 50.870218,-1.044337 50.870228,-1.044334 50.870239)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL